Portable Device and Method Of Communicating Medical Data Information

ABSTRACT

A portable medical device for communication of medical data information has a medical device part that includes a first processor and first storage means, and means for executing one or more medical related functions, a communication device part comprising a second processor, second storage means, and communication means. The medical device part and the communication device part are connected allowing for exchange of data information according to a predetermined protocol. The exchange of communication may be under the control of the medical device part, but the functionalities of each device part otherwise is separated providing for easy interchangeability of the communication device part or the medical device part. Also disclosed is a method for communication of medical data information.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation-In-Part of U.S. Non-Provisionalapplication Ser. No. 10/216,680 (filed on Aug. 2, 2002), and whichclaims the benefit of priority under 35 USC § 119 of U.S. ProvisionalApplication 60/315,085 (filed on Aug. 27, 2001) and Danish ApplicationPA 2001 01210 (filed Aug. 13, 2001), all of which are herebyincorporated by reference in their entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a portable medical device forcommunication of medical data information.

The present invention also relates to a method of communication ofmedical data information by a portable medical device.

2. Related Art

Product and software validation for medical products are troublesome,delays a product's time-to-market, time-consuming, complicates revisiontasks, and is expensive.

For example, in some jurisdictions, regulatory bodies govern theapproval of medical products (e.g., devices) according to presetvalidation standards for medical products. Likewise, regulatory bodiestypically also govern the approval of any software contained withinmedical products according to preset validation standards for medicalproduct software. For example, in the United States the Food and DrugAdministration (FDA) has issued a document entitled, “Design ControlGuidance for Medical Device Manufacturers,” on Mar. 11, 1997, whichprovides criteria for approval of medical product (e.g., device) designaccording to its established preset validation standards. Likewise, withregard to software, the FDA has issued a document entitled “GeneralPrinciples of Software Validation; Final Guidance for Industry and FDAStaff” on Jan. 11, 2002 (which supersedes an earlier document dated Jun.9, 1997), which provides criteria for approval of software according toits established preset validation standards.

Medical products (e.g., devices) can further include communication parts(e.g., Bluetooth, Radio frequency (RF) communication, Infrared (IR)communication, HTTP (Hyper Text Transmission Protocol), SHTTP (SecureHyper Text Transmission Protocol), TCP/IP (Transmission ControlProtocol/Internet Protocol), PPP (Point-to-Point), SSL (Secure SocketLayer), TLS (Transport Layer Security), GSM (Global System for Mobilecommunication), GPRS (General Packet Radio System), UMTS (UniversalMobile Telephone System), and IrDA, among others) of which the generaldesign and operation of the communication parts are governed and/orregulated by standards setting bodies which provide criteria forapproval of communication parts according to established presetvalidation standards.

It has heretofore been known to fully integrate communication parts andsoftware within the medical products, such that approval of each of thecommunication part, the medical product (e.g., device), and the softwareis required, each according to preset validation standards in theirappropriate technology and/or jurisdiction. However, the fullintegration of the communication part or software within the medicalproduct can require renewed approval of the entire medical product(i.e., device and software) if any revisions are made to either thecommunication part, medical product (e.g., device) itself, or anysoftware contained in the medical product. Thus, revisions of either thecommunication part, medical product (e.g., device) or any softwarecontained in the medical product can delay a product's time-to-market,be time-consuming, complicates revision tasks, and can be expensive.

Rapid development in the field of communication requires for frequentupdates of communication soft-, hard- and/or firmware in a medicaldevice. As a result medical product and software validation is requiredfor a medical device with updated communication means even though nochanges have been made to the medical application “part” of the device.

SUMMARY OF THE INVENTION

In view of the above disadvantages, the present invention provides amethod and device that avoids the need for further medical productvalidation (e.g., by jurisdictional regulatory bodies) when thecommunication part and/or software of a medical device is changed,updated, or revised.

Likewise, the present invention provides a method and device that avoidsthe need for further software validation (e.g., by jurisdictionalregulatory bodies) when the medical product (e.g., device) and/orcommunication part is changed, updated, or revised.

The present invention further provides a method and device that avoidsthe need for further communication part validation (e.g., by standardssetting bodies) when the medical product (e.g., device) and/or softwareof a medical device is changed, updated, or revised.

The present invention further provides for clearly separate criticalmedical application functionalities from the complex communicationsoftware, hardware and/or firmware in order to obtain maximum safety andreliability of the critical medical application.

The present invention can be achieved by a device of the aforementionedkind that comprises:

-   -   a medical device part comprising:    -   a first processor and first storage means, and    -   a means for executing one or more medical related functions,    -   a communication device part comprising:    -   a second processor, second storage means, and    -   a communication means,    -   wherein the medical device part and the communication device        part is connected allowing for exchange of data information        according to a predetermined protocol, the exchange of data        information is under the control of the medical device part and        where the functionalities of each device part otherwise is        separated.

Hereby, two physically and functionally separated parts/units areobtained where one part is a medical device part responsible forperforming medically related actions, measurements, calculations,exchange of data with other medical devices, etc. and another part is acommunication device part (just communication part in the following)responsible for receiving and transmitting information under the controlof the medical device. The medical device part controls thecommunication so the communication part cannot interrupt or requestservice(s) from the medical device part, thereby ensuring maximum safetyand reliability of the medical application(s).

In this way, when the parts (software, hardware, firmware, etc.) of thecommunication device needs to be upgraded, the integrity of the medicaldevice part is preserved and the need for any further medical productand software validation is avoided thereby reducing time-to-market,expenses, etc.

Furthermore, when changes to the medical device part hardware, software,and/or firmware are required then the scope of medical product andsoftware validation can be restricted to the medical device part andneed not involve the communication device part thereby simplifyingrevisions tasks, etc.

According to a preferred embodiment, the predetermined protocolcomprises the medical device part acting as a master and thecommunication device part acting as a slave where the exchange ofinformation is done by the medical device part polling the communicationdevice part.

In this way, a simple protocol may handle and connect the twoasynchronous systems/parts of the medical device in a very simplefashion and the communication part cannot interfere, interrupt and/ortransmit data/information to the medical part without its permission.

In one embodiment, the medical device part further comprises one or moreof:

-   -   a user interface,    -   at least one medical transducer,    -   discrete and/or substantially continuously body fluid analysis        means,    -   drug administration means, and    -   a short-range communication means for exchanging data        information with at least another medical device.

In this way, relevant medical functions, like blood glucose/body fluidlevel measurement(s), drug or insulin administration, may be integrateddirectly with the medical device, so that a user will always have amedical function ready at hand when using the medical device therebyavoiding the need for an extra medical device. Additionally, the medicaldevice may act as a data collection/exchange devicecollecting/exchanging data with other relevant medical devices usingshort-range communication.

In one embodiment, the at least another medical device is selected fromthe group of:

-   -   a drug administration device,    -   a body fluid analyser,    -   an insulin administration device,    -   a blood glucose monitor (BGM),    -   a continuous blood glucose monitor (CGM),    -   an inhaler,    -   a tablet dispenser,    -   a lipid monitor,    -   a pulse monitor,    -   a lancet device,    -   a storage container,    -   a balance,    -   and any other apparatus adapted to measure at least one        physiological parameter.

In one embodiment, the device further comprises a power supply supplyingthe communication device part with power where the power supply may beturned on and off under the control of the medical device part.

In this way, power usage may be saved/minimized by turning thecommunication part off when it is not used which is especially importantfor portable devices usually having a limited power supply.

In one embodiment, the communication means is adapted to communicateaccording to the Bluetooth protocol.

Hereby, a very simple way of connecting to other devices and/or networksare obtained.

In one embodiment, the communication means are adapted to communicateinformation according to one or more of:

-   -   Radio frequency (RF) communication,    -   Infrared (IR) communication,    -   HTTP (Hyper Text Transmission Protocol),    -   SHTTP (Secure Hyper Text Transmission Protocol),    -   TCP/IP (Transmission Control Protocol/Internet Protocol),    -   PPP (Point-to-Point),    -   SSL (Secure Socket Layer),    -   TLS (Transport Layer Security), and    -   IrDA,

In one embodiment, the communication means are adapted to communicatewith a wireless access point/a mobile terminal where the accesspoint/the terminal is adapted to communicate according to one or moreof:

-   -   GSM (Global System for Mobile communication),    -   GPRS (General Packet Radio System), and    -   UMTS (Universal Mobile Telephone System).

In this way, a great level of mobility is assured for the user of themedical device as well as being able to transmit relevant datainformation.

In one embodiment, the communication device part is adapted to exchangedata information with a central server via a wireless network accesspoint.

The invention also relates to a system for supplying data from aportable medical device to a third party, where the system is adaptedto:

automatically transmit data information from a portable medical deviceto a central server for storage in at least one database,

process said data information, in order to derive additionalinformation, and

automatically transmit at least a part of the additional information toa predetermined third party.

In this way, a relative/relatives may obtain an ease at mind since theyknow that they will receive information if anything is wrong or may bepotentially dangerous or they simply is automatically updated on theuser's current situation. This is especially useful for relatives ofelderly people, children, etc. using a medical device. A medicalprofessional may also receive relevant information in this manner.

In one embodiment, the processing is done at said server and/or at saidmedical device.

In one embodiment, the data information comprises informationrepresenting one or more of:

-   -   at least one blood glucose value,    -   at least one value representing a body fluid level,    -   at least one physiological parameter,    -   amount and/or type of administered medication,    -   amount and/or type of administered insulin,    -   a trend of a glucose or body fluid level,    -   a prediction of a glucose or body fluid level,    -   timestamp in- or excluding date,    -   amount of food,    -   measurement of physical activity,    -   notification of appointment,    -   inventory logistics, and    -   body characteristics.    -   warnings, and    -   symptoms.

In one embodiment, the system is adapted to transmit data informationfrom a portable medical device to a central server according to theBluetooth protocol using a wireless access point connected via a networkto the central server.

In one embodiment, the third parties are one or more of:

-   -   at least one relative,    -   at least one parent, and    -   at least one medical professional.

In one embodiment, the system is further adapted to exchange informationbetween the portable medical device and another medical device in orderto retrieve relevant data information.

The invention also relates to a system for collecting data informationfrom a number of portable devices, wherein the system is adapted to:

-   -   generate data information in a portable device, the data        information relating to a clinical trial of a medical device        and/or medical product,    -   automatically sending the data information from the portable        device to a central server for storage in a database, and    -   process said data information.

In this way, relevant information may then be automatically transmitteddirectly to a relevant server for high-quality data storage andcollection since the actual obtained data is obtained directly from theuser/patient and transmitted e.g. for further processing. This mayreduce the cost and the time-to-market of a new product since the datacollection from many medical devices taking part in the medical trialmay be automated. Additionally, the need for hand-written logs of theparticipants of the trial is avoided thereby eliminating possible typosand avoiding the need for manually inputting/scanning the logs into asystem for storage and processing.

The invention also relates to a method of communication of medical datainformation between

-   -   a medical device part comprising:    -   a first processor and first storage means, and    -   a means for executing one or more medical related functions, and    -   a communication device part comprising:    -   a second processor, second storage means, and    -   a communication means,    -   wherein the medical device part and the communication device        part exchanges data information according to a predetermined        protocol, the exchange of data information is under the control        of the medical device part and where the functionalities of each        device part otherwise is separated.

In one embodiment, the predetermined protocol comprises the medicaldevice part acting as a master and the communication device part actingas a slave where the exchange of information is done by the medicaldevice part polling the communication device part.

In one embodiment, the medical device part further comprises one or moreof:

a user interface,

-   -   at least one medical transducer,    -   discrete and/or substantially continuously body fluid analysis        means,    -   drug administration means, and    -   a short-range communication means for exchanging data        information with at least another medical device.

In one embodiment, the at least another medical device is selected fromthe group of:

-   -   a drug administration device,    -   a body fluid analyser,    -   an insulin administration device,    -   a blood glucose monitor (BGM),    -   a continuous blood glucose monitor (CGM),    -   an inhaler,    -   a tablet dispenser,    -   a lipid monitor,    -   a pulse monitor,    -   a lancet device,    -   a storage container,    -   a balance, and    -   any other apparatus adapted to measure at least one        physiological parameter.

In one embodiment, the method further comprises controlling a powersupply by the medical device part, where the power supply supplies thecommunication device part with power.

In one embodiment, said communication means communicates according tothe Bluetooth protocol.

In one embodiment, said communication means communicates informationaccording to one or more of:

-   -   Radio frequency (RF) communication,    -   Infrared (IR) communication,    -   HTTP (Hyper Text Transmission Protocol),    -   SHTTP (Secure Hyper Text Transmission Protocol),    -   TCP/IP (Transmission Control Protocol/Internet Protocol),    -   PPP (Point-to-Point),    -   SSL (Secure Socket Layer),    -   TLS (Transport Layer Security), and    -   IrDA,

In one embodiment, said communication means communicates with a wirelessaccess point/a mobile terminal where the access point/the terminalcommunicates according to one or more of:

-   -   GSM (Global System for Mobile communication),    -   GPRS (General Packet Radio System), and    -   UMTS (Universal Mobile Telephone System).

In one embodiment, the communication device part exchanges datainformation with a central server via a wireless network access point.

The invention also relates to a method of supplying data from a portablemedical device to a third party, the method comprising the steps of:

-   -   automatically transmitting data information from a portable        medical device to a central server for storage in at least one        database,    -   processing said data information, in order to derive additional        information, and    -   automatically transmitting at least a part of the additional        information to a predetermined third party.

In one embodiment, said processing is done at said server and/or at saidmedical device.

In one embodiment, said data information comprises informationrepresenting one or more of:

-   -   at least one blood glucose value,    -   at least one value representing a body fluid level,    -   at least one physiological parameter,    -   amount and/or type of administered medication,    -   amount and/or type of administered insulin,    -   a trend of a glucose or body fluid level,    -   a prediction of a glucose or body fluid level,    -   timestamp in- or excluding date,    -   amount of food,    -   measurement of physical activity,    -   notification of appointment,    -   inventory logistics, and    -   body characteristics.    -   warnings, and    -   symptoms.

In one embodiment, said step of transmitting data information from aportable medical device to a central server is done by transmitting saiddata information according to the Bluetooth protocol using a wirelessaccess point connected via a network to the central server.

In one embodiment, said third parties are one or more of:

-   -   at least one relative,    -   at least one parent, and    -   at least one medical professional.

In one embodiment, said method further comprises the step ofcommunicating between the portable medical device and another medicaldevice in order to retrieve relevant data information.

Finally, the invention also relates to a method of collecting datainformation from a number of portable devices, the method comprising thesteps of:

-   -   generating data information in a portable device, the data        information relating to a clinical trial of a predetermined        medical product and/or device,    -   automatically sending the data information from the portable        device to a central server for storage in a database, and    -   processing said data information.

The method and embodiments thereof correspond to the device andembodiments thereof and have the same advantages for the same reasons,and therefore will not be described again.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a schematic block diagram of a medical device according tothe present invention;

FIG. 2 shows a more detailed schematic block diagram of a medical devicecomprising a Bluetooth communication device part;

FIG. 3 illustrates the communication between a medical device part and aBluetooth communication device part;

FIGS. 4 a and 4 b illustrates examples of the communication between amedical device and other devices according to the present invention;

FIG. 5 illustrates the communication between a Bluetooth communicationdevice part and a central Internet server;

FIG. 6 a illustrates the short-range communication between a medicaldevice according to the present invention and other medical devices;

FIG. 6 b illustrates communication between a medical device according tothe present invention and other medical devices;

FIGS. 7 a-7 c illustrate examples of various embodiments of theshort-range communication means.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 shows a schematic block diagram of a medical device according tothe present invention. Shown is a medical device (100) comprising anintegrated medical device part (101) (denoted medical part in thefollowing) and an integrated communication device part (102) (denotedcommunication part in the following).

The medical part (101) comprises one or more firstmicroprocessors/processing means (104), a first storage/storagemeans/memory means (103), and means for providing/performing medicalrelated functionalities (106) like medically related actions,measurements, calculations, etc.

The means for providing medical functionalities (106) may e.g. compriseone or more of body fluid analyser means, drug administration means,and/or short-range communication means for communicating with at leastanother medical device and may operate under the control of a separateprocessor (not shown), again being controlled by the first processor(104), or under the control of the first processor (104) directly.

The communication part (102) comprises one or more secondmicroprocessors/processing means (104′), a second storage/storagemeans/memory means (103′), and communication means (105) forcommunicating with and/or via other devices.

The medical part (101) and the communication part (102) are connectedallowing for exchange of date between them via a physical interface(like a simple electrical connection) where the exchange of data happensaccording to an interface layer (107) located in and under the controlof the processor (104). The interface layer (107) comprises a suitableprotocol and is under the complete control of the processor (104) of themedical part (101). A suitable protocol may e.g. be a protocol where themedical part (101) operates as a master and the communication part (102)operates as a slave as indicated by the one-way arrow (109) (even thoughexchange of information is allowed in both directions). In this way, twophysically and functionally separated parts/units (101; 102) areobtained as indicated by the line (108) where a medical part (101) isresponsible for performing medically related actions, measurements,calculations, etc. and another part (102) is a communication partresponsible for receiving and transmitting information under the controlof the medical device. Hereby, the critical medical applicationfunctionalities is clearly separated from the complex communicationsoftware, hardware and/or firmware giving maximum safety and reliabilityof the critical medical application.

Preferably, the medical device (100) further comprises a user interface(not shown) for receiving and/or presenting information from/to a userof the medical device (100). The user interface preferably comprisesinput means like buttons, scroll-wheels or the like and output meanslike a display or combined input-output means like a touch sensitivedisplay like already known in the art.

The first and second storage/memory means (103; 103′) may e.g. be anon-volatile memory, a volatile memory or a combination of both.Examples are flash memory, RAM, ROM, EEPROM, magnetic and/or opticstorage means, etc.

The first (104) and second (104′) processing means/processors maycomprise one or more general or special purpose micro-processors or amix hereof.

The communication means (105) preferably communicates according to theBluetooth standard/protocol. Alternatively, communication via RF, IR, awire/cable is used according to a suitable protocol.

FIG. 2 shows a more detailed schematic block diagram of a medical devicecomprising a Bluetooth communication part. Shown is a medical part (101)and a communication part (102) corresponding to the one shown in FIG. 1.

The communication part (102) comprises a Bluetooth communication coreand is adapted to communicate with external devices according to thewell-known Bluetooth protocol. The Bluetooth core/the Bluetooth protocolstack comprises an Interface Layer interfacing with the medical part(101). The Interface Layer comprises in one embodiment an XML Glue-layerfor generating, providing, handling, etc. XML scripts thereby allowingfor a receiver to handle/execute these scripts directly. The protocolstack of the communication part (102) also comprises the TCP/IP(Transmission Control Protocol/Internet Protocol) and PPP(Point-to-Point Protocol) protocols connected to the Interface Layer viathe XML Glue-layer. An RFComm (a serial emulation protocol) manager isconnected to the TCP/IP/PPP protocol manager. The Bluetooth Core alsocomprises a Service Discovery Protocol (SDP) manager that is responsibleto determine which services are available from Bluetooth enabled serviceservers like a PC or a mobile telephone offering services like Internetand/or Network connection, etc. or other types of services. The SDPmanager is also connected to the Interface Layer. Both the SDP and theRFComm manager are connected to a L2CAP (Logical Link Control andAdaption Protocol) manager (responsible for channel establishment) thatis connected to a Link Manager (LM) (responsible for linkestablishment). The Bluetooth Core also comprises a Baseband and aBluetooth Radio specification responsible for the radio communicationaccording to the Bluetooth specification. Information regarding theBluetooth protocol may e.g. be obtained at www.bluetooth.comincorporated herein by reference.

The communication steps between the medical device part (101) and acommunication part (102) using Bluetooth are explained in greater detailin connection with FIG. 3.

The medical part (101) comprises a user interface for receiving and/orpresenting information from/to a user of the medical device in the formof input means (202) like buttons, scroll-wheels, etc. and output meanslike a display (201) or combined input-output means like a touchsensitive display as signified by the double arrow in parenthesis. Themedical part (101) also comprises a memory (103) for storing software,firmware, relevant data/information, etc. The medical part alsocomprises a real-time clock (RTS) (110) for enabling time- anddate-stamps of generated/provided information like time-stamping aglucose/body fluid level measurement, a drug/insulin administration,etc.

Furthermore, the medical part (103) comprises one or more medicalfunction(s) (106) like described in connection with FIG. 1. In thisparticular embodiment the medical device part (101) comprises anintegrated medical transducer or a medical potentiostat like a bodyfluid analyser or more particularly a BGM (blood glucose monitor),either a continuous (CGM) or a discreet monitor. An additional medicalfunction in this particular embodiment is (e.g. very) short-rangecommunication means (106′) so that the medical device part (101) maycommunicate with another medical device (405), like a drugadministration unit, an insulin pen, an insulin doser, an inhaler,tablet dispenser, etc., in a very simple manner thereby allowingexchange of relevant information/data like type and amount/dose ofadministered medication and a corresponding time/date-stamps. Theinformation may e.g. be generated during use of the other medicaldevice(s) and stored there until transferred to the medical part (101).These short-range communication means may e.g. be opticallycommunication means like a Infrared transmitter/receiver pair (106′)where communication is initiated automatically when the additionalmedical device is docked with or fitted to the medical communicationdevice (100) or simply is in close proximity. Alternative short-rangecommunications means are inductive or electronic communications meansthat are explained in greater detail in connection with FIGS. 7 a-7 c.

Alternatively, the communication part (102) may be used to exchangeinformation with other medical devices (405) thereby avoiding the needfor short-range communications means (106′), however the short-rangecommunications means (106′) would typically require less power andallows for simple, easy and transparent, for the user, (if communicationis initiated when docking the device) exchange of information.

The medical device part (101) and communication part (102) are separatedlike described before and signified by the line (108) and connectedallowing only for exchange of data under the strict control (assignified by the one-way arrow (109)) of the medical device part (101).

The medical device preferably also comprises a power supply (203) to thecommunication part (102) that is controlled by the medical device part(101). In this way, the communication part (102) may be turned off inorder to conserve power.

FIG. 3 illustrates the communication between a medical part and aBluetooth communication part. Shown are the communication steps betweenthe medical device part (101) and the communication device part (102).

The medical device part (101) comprises an application layer, a MedicomLayer (corresponds to (106) in FIGS. 1 and 2) and an Interface Layer(corresponds to (107) in FIG. 1). The medical device part (101)comprises the Bluetooth core shown and described in connection with FIG.2.

Communication may e.g. be initiated either on user request, request by amedical application in the medical device part (101) (e.g. on the basisof an obtained measurement from an integrated medical transducer), aninternal request by the medical device (100), by docking another medicaldevice with the medical device (100) and/or using short-rangecommunication means (106′) with an additional medical device like adoser, a CGM, inhaler, a BGM, etc.

When a request for Bluetooth communication via the communication devicepart (102) is generated, the medical part (101) generates a Bluetoothpower-up by activating the power supply (203 in FIG. 2) if thecommunication part (102) is not already powered. Then a request for aBluetooth link to a relevant information receiver is sent to thecommunication part (102). The communication part (102) establishes asuitable link and returns an acknowledgement after which the actualcommunication/transmission of data may begin. If no establishment of acommunication link is possible or communication is impossible foranother reason, the relevant information is kept and may be triedtransmitted at another time, e.g. when the user uses the medical device(100) the next time. Preferably, the communication part (102) isswitched off when it is determined that no communication is currentlypossible in order to conserve power usage. A warning may be presented tothe user specifying that communication was not possible, but preferablythe communication takes place without the user's specific knowledge anda warning may e.g. only be presented to the user if no datacommunication was possible after a given number of tries or within agiven period of time dependent on the actual application of the medicaldevice (100).

After a Bluetooth link is successfully established, a first framecomprising an amount of data/information is sent to the communicationpart (102) where the frame is transmitted via the Bluetooth radiotransmitter. The communication part (102) reports when the informationhas been transmitted, i.e. when a frame buffer is empty. The steps ‘sendframe’ and ‘report empty buffer’ repeats/loops until the complete amountof information has been sent, i.e. N frames of information has beentransmitted via Bluetooth radio communication. After the medical part(101) receives a ‘frame buffer empty’ and no further information has tobe sent, the medical part (101) may send a request for receipt of theBluetooth communication from the communication part (102). Thecommunication part (102) returns a receipt of the Bluetoothcommunication with the relevant information receiver to the medicaldevice part (101), which then executes a power-down of the communicationpart (102) in order to conserve power if no additional information is tobe exchanged.

The communication between the communication part (102) and a relevantinformation receiver is explained in connection with FIGS. 4 a, 4 b and5.

FIGS. 4 a and 4 b illustrates examples of the communication between amedical device and other devices according to the present invention.

FIG. 4 a illustrates communication between a medical device (100) and amobile communications terminal (402) belonging to a relevant third partyvia a mobile communications terminal/a wireless access point (401),belonging to a user of the medical device (100), to a network/theInternet. The medical device (100) preferably communicates with the userterminal (401) according to the Bluetooth protocol like described inconnection with FIGS. 2 and 3, thereby establishing a Bluetoothcommunications link between the communication device part of the medicaldevice (100) and the user's terminal (401). Alternatively, thecommunication between the medical device (100) and the user's terminal(401) may be done via IR communications means, a cable connecting them,other radio frequency (RF) communications means, etc.

When the Bluetooth communications link is established information may betransmitted to a terminal (402) of a relevant third party using a GSM(Global System for Mobile communication), UMTS (Universal MobileTelephone System) and/or GPRS (General Packet Radio System)communication network or another wireless communication network, so thatrelevant information may be exchanged between the user's terminal (401)(and thereby the medical device (100)) and the terminal (402). Theinformation may e.g. be exchanged between the terminal (401) and theterminal (402) using SMS (Short Message Service) or e-mail as a carrier(e.g. sending SMS messages/e-mails alternating in both or in onedirection only) or alternatively, a two-way data communication betweenthe terminals (401; 402).

A relevant third party may e.g. be a medical professional, a care-team,etc. and/or a relative of the user.

In this way, a medical professional may, e.g. automatically, receivestatus reports of the user at a regular time interval or when dangerousor potentially dangerous situation occurs or is about to occur, e.g.when a critical body fluid/blood glucose level being outside apredetermined interval has been determined and/or estimated (for afuture time) by the medical device (100). Additionally, the professionalmay send relevant information, like an updated medical regime and/ortarget body fluid/blood glucose level interval, suggested action for agiven situation (e.g. administer X amounts of type Y medication) e.g. inresponse to information/data received from the user's terminal (401)/themedical device (100). This enables a very close and precise monitoringof the user since data/information may be transmitted to a professionalregularly in an easy and transparent manner and the data/information maybe obtained directly by the medical device (100) and/or other devices(BGM, CGM, insulin doser, drug administration device, body fluidmonitor, etc.) in communication and/or integrated with the medicaldevice (100).

A medical professional may also determine when the user has to be calledin for a consultation, check-up, etc. based on actual receivedinformation instead of having regular consultations. In this way, a useronly needs to attend a consultation when there is an actual need.Additionally, the professional is better prepared since the relevantinformation is available to him in advance of an consultation.

Another application of the present invention is that one or morerelatives of the user of the medical device (100) automatically mayreceive a status report or information from the medical device (100) viathe terminal (401) regarding how the user's situation is and/or going tobe in the near future. The transmitted information may e.g. containtime/date, type and/or amount of administered medication, time/date andvalue of performed measurement(s), compliance with a medical regime,etc. or simply just a status e.g. ‘Status is ok’, ‘possible problem(s)’,‘Serious problems’, ‘X follows the medical regime fully’, ‘X has a BGLwithin the target range’, etc.

In this way, a relative/relatives obtains an easy at mind since theyknow that they will receive information if anything is wrong or may bepotentially dangerous or they simply is automatically updated on theuser's current situation. This is especially useful for relatives ofelderly people, children, etc. using a medical device (100).

The medical device (100) may also receive and/or transmit relevant datainformation with one or more external medical related devices (405) asdescribed later in greater detail in connection with FIGS. 6 a and 6 b.

FIG. 4 b illustrates communication between a medical device (100) and adatabase server (403). The communication between the medical device(100) and the terminal (401) is like described in connection with FIG. 4a. Information/data received from the medical device (100) istransmitted by the terminal (401) to a server (403) preferably using theTCP/IP and PPP protocols and GPRS for high-speed data communication.Alternatively, a GSM or a UMTS network may be used. The server (403) maye.g. be an Internet database server. The server (403) receives therelevant information and stores it and determines what is to happen withthe information e.g. where it/a copy is to be transmitted and/or stored,if and how it is to be processed, etc.

The server (403) may transmit the information to a number of mobileterminals (403) and/or computers (404) e.g. as an SMS message, an e-mailand/or in a suitable data format. Additionally, a computer (404) and/ora terminal (402) may also connect to the server (403) using standardbrowser software or WAP (Wireless application Protocol) in order toaccess, retrieve, etc. the relevant stored information, preferably,after specifying a valid password and user-name. In this way, either aclient, a relative to a user and/or a medical professional may obtaineasy access to the stored historical medical data and/or derivations(e.g. processed) thereof.

The secure socket layer (SSL)/transport layer security (TLS) may also beused by the communication devices in this system (one or more ofterminal (401), terminal (402), the medical device (100), the server(403), the computer (404)) in order to enhance the security of theinformation. Bluetooth incorporates the possibility of using built-insecurity by finding devices, pairing devices, authentication, andencryption thereby enhancing the security between the medical device(100) and the terminal (401).

Applications of the embodiment shown in FIG. 4 b corresponds to theapplications described above in connection with FIG. 4 a.

Yet another application of the present invention is that it may be usedin connection of a clinical trial of a new medical product (new/modifieddrug, new measurement device, new drug administration device). Datacollected by the medical device (100) and other related medical devices(405) may then be automatically transmitted directly to the relevantdatabase server (403) for high-quality data storage and collection sincethe actual obtained data is obtained directly from the user/patient andtransmitted e.g. for further processing. This may reduce the cost andthe time-to-market of a new product since the data collection from manymedical devices taking part in the medical trial may be automated.Additionally, the need for hand-written logs of the participants of thetrial is avoided thereby eliminating possible typos and avoiding theneed for manually inputting/scanning the logs into a system for storageand processing.

Alternatively, the mobile terminal (401) and/or the mobile terminal(402) may be an electronic device like a laptop, a PC, a PDA, etc.equipped with communication and/or a gateway (e.g. integrated, a networkinterface card (NIC), modem, etc.) to the Internet, a cellular networklike a GSM, GPRS, UMTS network, etc. or another kind of communicationsnetwork. The communication between the device (401) and the medicaldevice (100) may e.g. be done via/according to the Bluetooth protocol oranother RF communication protocol, IrDA (Inrared Data Association)protocols, a cable connection, etc.

One example of the use of the medical device (100) according to thepresent invention will be illustrated by the following use-case thatdescribes a typical for a diabetic user equipped with a medical device(100) according to the invention.

At 7.00. The user gets out of bed and takes his cap unit with integratedBGM/medical device (100) and measures the glucose content of his blood.

The medical device (100) records this event with a time stamp and savesit in the memory/an electronic log book. Then the medical device (100)searches for a wireless access point (401) to the Internet, and iffound, non-replicated data are transferred from the electronic log bookto a server.

The user then decides to take x units of actrapid (making ready for hisbreakfast), he takes an insulin doser/insulin administration device(405) which he has already dedicated to be his actrapid doser andinjects x units of actrapid. After the injection the actrapid doser(405) is placed in, docked with, brought in short-range communicationrange with, etc. the cap unit/medical device (100).

The doser (405) will now make contact to the cap/medical device (100)e.g. by means of an IR diode and an IR transistor to transfer dose size,insulin type, relative time stamp and doser status to the cap.

The cap/medical device (100) transfers setup data, if any, to the doser(405). The cap can now calculate the absolute time of this event andtransfers it to the electronic log book.

The medical device (100) now searches for a wireless access point (401)to the Internet, and if found, non-replicated data are transferred fromthe electronic log book to a server (403).

At 8.00. The user has his breakfast.

At 9.00. The user arrives at his job, he decides (optionally the medicaldevice (100) reminds him) to make a control measurement of the glucosecontent of his blood.

The medical device (100) records this event with a time stamp and savesit in the electronic log-book. The medical device (100) then searchesfor a wireless access point (401) to the Internet, and if found,non-replicated data are transferred from the electronic log-book to aserver (403).

At 12.00. The user decides to measure the glucose content of his bloodagain.

The medical device (100) records this event with a time stamp and savesit in the electronic log-book. The medical device (100) then searchesfor a wireless access point (401) to the Internet, and if such an accesspoint is found, non-replicated data are transferred from the electroniclog-book to a server (403).

He now decides to take x units of actrapid (making ready for his lunch).After the injection he places his actrapid doser in the cap/medicaldevice (100).

The doser (405) will now make contact to the cap/medical device (100) bymeans of an IR diode and an IR transistor to transfer dose size, insulintype, relative time stamp and doser status to the cap unit/medicaldevice (100).

The cap/medical device (100) transfers setup data, if any, to the doser(405). The cap/medical device (100) can now calculate the absolute timeof this event and transfers it to the electronic log-book.

The medical device (100) then searches for a wireless access point (401)to the Internet, and if such a point is found, non-replicated data aretransferred from the electronic log-book to a server (403).

At 12.30. The user has lunch.

At 13.30. The user decides (optionally the medical device (100) remindshim) to make a control measurement of the glucose content of his blood.

The medical device (100) records this event with a time stamp and savesit in the electronic log book. The medical device (100) then searchesfor a wireless access point (401) to the Internet, and if found,non-replicated data are transferred from the electronic log book to aserver (403).

At 17.00. The user decides to measure the glucose content of his bloodagain.

The medical device (100) records this event with a time stamp and savesit in the electronic log book. The medical device (100) then searchesfor a wireless access point (401) to the Internet, and if found,non-replicated data are transferred from the electronic logbook to aserver (403).

He now decides to take x units of actrapid (making ready for hisdinner). After the injection he places his actrapid doser (405) in thecap/medical device (100).

The doser (405) will now make contact to the cap/medical device (100) bymeans of an IR diode and an IR transistor to transfer dose size, insulintype, relative time stamp and doser status to the cap/medical device(100).

The cap/medical device (100) transfers setup data, if any to the doser(405). The cap/medical device (100) can now calculate the absolute timeof this event and transfers it to the electronic log book.

The medical device (100) then searches for a wireless access point (401)to the Internet, and if is found, non-replicated data are transferredfrom the electronic log book to a server (403).

At 18.00. The user has his dinner.

At 19.00. The user decides (optionally the medical device (100) remindshim) to make a control measurement of the glucose content of his blood.

The medical device (100) records this event with a time stamp and savesit in the electronic log book. The medical device (100) then searchesfor a wireless access point (401) to the Internet, and if found,non-replicated data are transferred from the electronic log book to aserver (403).

At 23.00. The user decides to go to bed. He measures the glucose contentof his blood.

The medical device (100) records this event with a time stamp and savesit in the electronic log-book. The medical device (100) then searchesfor a wireless access point (401) to the Internet, and if such a pointis found, non-replicated data are transferred from the electroniclog-book to a server (403).

He now decides to take x units of insulatard (basic level for thenight). He takes another doser (405) which he has already dedicated tobe his insulatard doser and injects x units of insulatard. After theinjection he places his insulatard doser (405) in/brings withinshort-range communication range of the cap/medical device (100).

The doser (405) will now make contact to the cap/medical device (100) bymeans of an IR diode and an IR transistor to transfer dose size, insulintype, relative time stamp and doser status to the cap/medical device(100).

The cap/medical device (100) transfers setup data, if any. to the doser(405). The cap/medical device (100) can now calculate the absolute timeof this event and transfers it to the electronic log book.

The medical device (100) then searches for a wireless access point (401)to the Internet, and if found, non-replicated data are transferred fromthe electronic log book to a server (403).

The user possibly checks whether the medical device (100) containsnon-replicated data, and if he finds that it is necessary to connect tohis server, he activates a user menu in the medical device (100), whichwill immediately try to make contact to the server (403).

The medical device (100) then searches for a wireless access point (401)to the Internet, and if such an access point (401) is found,non-replicated data are transferred from the electronic log-book to aserver (403).

FIG. 5 illustrates the communication between a Bluetooth communicationdevice part and a central Internet server. Shown is a medical device(100) comprising a medical part (101) and a communication part (102)like described earlier. The communication part (102) comprises in thisparticular embodiment a Bluetooth communication core. The two parts(101; 102) is connected via an Interface Layer of each part so that thecritical software, etc. handling the medical related function(s) of themedical device (100) is clearly separated. The medical relatedfunction(s) of the medical device (100) is illustrated by an ApplicationLayer. The Interface Layer(s) connects and handles the two asynchronoussystems/parts (101; 102) using polling by the medical part (101),assigned as master, of the communication part (102), assigned as aslave. In this way, the communication part (102) may not interfere,interrupt and/or transmit data/information to the medical part (101).

A XML Medicom Layer in the medical part (101) is also shown and isresponsible for retrieving data/information to be transmitted from thememory of the medical part (101), calculate a check-sum (e.g. CRC) ofthe information and format it into a suitable format e.g. a XML formatwhere the information e.g. is formatted into a number of frames eachcomprising a number of fields.

An example of fields in a frame for a given format is:

Length Name of Data field (chars) Description DeviceID 10 10 chars usedfor unique identification of the medical device. DeviceVer 4 4 charsused for definition of an actual XML-scheme used. DeviceTime 12 Atimestamp (e.g. mmddyyhhmmss). FrameCount 10 Indicates FRAME number.EventType 12 Indicates data type, etc. Note 1 EventTime 12 A timestampfor a given event (e.g. mmddyyhhmmss). EventSize 4 Value for event (e.g.amount of administered medication or value for measured medical value.CheckSum 8 A calculated check-sum value for the information contained inthe frame.

In one example/embodiment events being communicated may be identifiedby:

Event_Type=INS-S-001 indicates an event where short-acting insulin oftype 1 was administered.

Event_Type=INS-S-XXX indicates an event where short-acting insulin oftype ‘xxx’ was administered.

Event_Type=INS-L-001 indicates an event where long-acting insulin oftype 1 was administered.

Event_Type=INS-L-YYY indicates an event where long-acting insulin oftype ‘yyy’ was administered.

Event_Type=INS-M-001 indicates an event where mix-acting insulin of type1 was administered.

Event_Type=INS-M-ZZZ indicates an event where mix-acting insulin of type‘zzz’ was administered, etc.

Event_Type=BGM-mmol/l indicates an event where a body fluidmeasurement/a blood glucose measurement (BGM) is done in mmol/l.

Event_Type=BGM-mg/dl indicates an event where a body fluid measurement/ablood glucose measurement (BGM) is done in mg/dl, etc.

Event_Type=BGM-mmol/l-k indicates an event where a calibration of aBGM/medical transducer is done in mmol/l.

Event_Type=BGM-mg/dl-k indicates an event where a calibration of aBGM/medical transducer is done in mg/dl, etc.

Event_Type=STRIPCODE indicates an event where a new strip-code, numberidentifier, bar-code, etc. for a given type of medication is inputtedinto the medical device (100).

Each Event_Type has an associated value (if applicable) specifying theactual value associated with the reported event. The range andresolution depends on the given event, e.g. may the values for a giventype of medication/insulin cover the values 0-999 units (UI) with aresolution of 1/10, a new strip-code may cover the values 0-999 with aresolution of 1, a calibration in mg/dl may cover 0-999 with aresolution of 1, a calibration in mmol/dl may cover 0-99 with aresolution of 1/10, a BGM/body fluid measurement event in mg/dl maycover 0-999 with a resolution of 1, a BGM/body fluid measurement eventin mmol/dl may cover 0-99 with a resolution of 1, etc.

The relevant information/frames is exchanged with the Bluetooth corelike described in connection with FIG. 3 and transmitted to a Bluetoothsupporting communication device/a mobile terminal (401) according to theBluetooth protocol.

The relevant information/frames is sent via the mobile terminal (401)e.g. using GPRS, as described earlier, via a cell phone provider (502)and the Internet/a network (503) to a database server (403).

Preferably, a firewall (501) is connected between the Internet/thenetwork (503) and the database server (403) in order to enhance thesecurity of the server (403) by prohibiting unauthorised communication.The server (403) may be accessed and may process, transmit and/orreceive information like described earlier.

Preferably, the server site also comprises a HTTP server connectedbetween the firewall (501) and the database server (403) for handlingrequests from browsers according to the HTTP protocol.

The communication between the medical device (100) and the databaseserver (403) may use encryption of communication and the web site(comprising the server(s)) may be secured using HTTPS/SSL (or HTTPS/TLS)communication.

The communication between the medical device (100) and the server (403)is preferably substantially a one-way communication (from the device tothe server) (although necessary handshakes, receipts, etc. istransferred to the medical device (100)). If applicable, information,e.g. updated data/information, like recommended medical regimes, etc.,is also transferred from the server (403) to the medical device (100).

FIG. 6 a illustrates the short-range communication between a medicaldevice according to the present invention and other medical devices.Shown are a mobile medical device (100), two additional medical devicesthat in this particular example are two drug administration devices(405) containing different types of medication, e.g. fast- andslow-acting insulin, and a CGM/biosensor (601) like a glucose biosensor.

The dosers (405) comprises input means e.g. a turning wheel (611) foradjusting, either electronically or manually, the level/amount ofmedication to be administered, activation/input means (616) forinitiating the administration of medication and a display (612) thatshows the currently selected amount of medication to be administeredwith text, icons, graphic representations, etc. The doser (405)preferably has processing means and storage facilities, like a CPU andRAM, for processing and storing data, like the time, date and amount ofmedication of the last couple of administrations. This information canbe shown in the display (612) e.g. on request.

The doser (405) further comprises a cartridge (613) that contains themedication to be administered, and is fitted with a needle (614) throughwhich the medication is administered. The doser (405) has a transparentwindow (615) so that the amount of medication left in the cartridge(613) can readily be identified.

Cartridges (613) may contain different types of insulin, like fast andslow acting insulin, a mix-acting, etc., and the user mayinsert/exchange a cartridge (613) of a given type when needed and/or usemultiple dosers (405) with different types of medication (e.g.fast-acting and slow-acting insulin).

The dosers (405) are also provided with short-range communications means(617) for receiving and transmitting information and datarepresentations from and to other devices as will be described in thefollowing. Alternatively, a doser (405)/an additional medical device(405) may be provided with wireless communications means/a wirelesstransceiver, as indicated by the arrow in parenthesis, instead or incombination with the short-range communications means (617).

The CGM (601) is a device that monitors/measures the blood glucoselevel/concentration of a user continuously and comprises, in thisembodiment, a base unit and a glucose biosensor (603).

The CGM base unit is in this embodiment the medical device (100) or morespecifically the medical device part (101) being in communication withthe biosensor (603). Alternatively, a separate CGM base unit may beprovided that communicates with the medical device (100).

The glucose biosensor (603) is mounted on an adhesive (602) located onan appropriate part of the user's body like the stomach, upper arm, etc.and is located subcutaneous, i.e. in the external fat, in the user'sbody.

The biosensor (603) preferably comprises a potentiostat where a fixedpotential can be applied between two electrodes of the biosensor herebymeasuring the current that the work electrode of the biosensor produces.The generated current is proportional to the glucose concentration inthe blood of the user.

The generated current is transmitted via a wire/cable or wirelesscommunication means like IR transceivers, RF transceivers, etc. to theCGM base unit (100) for a translation/interpretation from a continuoussignal into a representation for later processing. Preferably thistranslation is performed by a standard A/D converter with a samplingrate which at least is faster than the worst case change of the BGL soeven the fastest change is ‘captured’ by the CGM (601)/CGM base unit(100). A sampling rate may e.g. be once every couple of minutes.

Alternatively, the sampling takes place at the biosensor (601) and onlythe sampled values are transmitted to the CGM base unit (100).

The converted measurement/continuous values may be presented to the uservia displaying means (606) like a LCD display, etc.

The converted measurements are kept in a memory for later retrieval,analysis, and etc. so a detailed history log of sampled measurements maybe obtained. This detailed history log may e.g. be used to predict atrend for the BGL of a user thereby enhancing the information value forthe user.

In one embodiment the BGL measurement is converted into a correspondingamount of insulin needed to bring the user into compliance and displayedon the display (606).

The biosensor (603) is preferably calibrated on a regular basis, e.g.each day, by external calibration e.g. by a traditional blood glucosemonitor (BGM) system, in order to ensure the best accuracy. Typicallythe biosensor (603) will have to be replaced after e.g. three days ofuse and be calibrated once each day.

Alternatively, the CGM may be embodied by other invasive, semi-invasiveor non-invasive systems.

In a preferred embodiment, the medical device (100) is a protective capunit comprising an integrated blood glucose monitor (BGM), and oneadditional medical device (405) is an insulin administration devicearranged so that they automatically transmit, via short-rangecommunications means, relevant data information between them when thedevices are mutually positioned in a suitable communication position,e.g. when the cap unit/the medical device (100) is fitted onto, dockedwith/onto, clicked-on, screwed-into, snapped-with, etc. with theadditional medication device (405).

Alternatively, the additional medication device (405) may be anothertype of drug administration device like a pen, syringe, inhaler, tabletdispenser, etc. or in general any medication administration device.

In this way, simplicity for the user is obtained, since the devicesautomatically store and exchange data information as part of the normaluse.

The cap unit/medical device (100) can be fitted to an additionalmedication device (405) so that one single compact unit and protectionof the additional medication device (405) is obtained.

In this way, the user does not have to worry about collecting datainformation in a separate log-book and additionally, the datainformation may be collected in a single apparatus for furtherprocessing, transmission and/or use. In this way, a complete log-book isobtained in e.g. a single device, which may be used by the user with thehelp of the devices to obtain detailed information of trends, currentand/or previous state(s), re-occurring events, e.g. that adverse effectsrelating to the self-treatment occur every Sunday by using/analysing forbehavioural and/or measured physiological patterns.

The short-range communications means (617) is preferably an infrared(IR) communications means/transceiver providing IR communication of datainformation between the medical device (100) and the additionalmedication device (405).

Alternatively, the short-range communications means (617) is aninductive means i.e. comprising inductive coils or the like in eachdevice.

As another alternative, the short-range communications (617) is aelectrical communications means, i.e. a simple switch mechanism that maybe used to transfer data information between devices.

The embodiments of the short-range communication means (617′) areexplained in greater detail in connection with FIGS. 7 a-7 c.

Additionally, the energy/power used for communication between theapparatuses is minimized and/or reduced since only (very) short-rangecommunication needs to be used when the cap/medical device (100) isfitted on, etc. to the additional medication device (405). This is veryimportant, especially for portable apparatuses, since reduced energyconsumption extends the time between the need for charging a powersource of the apparatuses, like a battery, etc., prolongs the time wherethe apparatuses may be used and/or extends the life-time of anon-chargeable power source.

FIG. 6 b illustrates communication between a medical device according tothe present invention and other medical devices. Shown are a medicaldevice (100) according to the present invention, a CGM biosensor (601),a drug administration device (405), a schematic representation ofadditional medical device(s) (405), and a general base unit (620).

The general base unit (620) comprises a display (621), a user interfaceand, preferably, wireless communication means/a wireless transceiver forcollecting and/or exchange relevant data information from the otherdevices (601, 405). The information may be viewed at the display (621)and stored at the base unit (620) and be transmitted to the medicaldevice (100) using short-range communication means (617) when docking,fitting, clicking-on, screw-into, snap-with, etc. the medical device(100) and the base unit (620), as described earlier. Alternatively, thebase unit (620) and the medical device (100) is provided with wirelesscommunications means/a transceiver instead or in addition to theshort-range means (617), as indicated by the arrow in parenthesis.

The additional medical device(s) (405) may comprise a tablet dispenser,inhaler, a balance, body fluid measure device, drug administrationdevice or in general other diabetes relevant data sources.

In this way, an easy way of obtaining additional information fromvarious other relevant devices is provided.

FIGS. 7 a-7 c illustrate examples of various embodiments of theshort-range communication means.

FIG. 7 a illustrates an embodiment of the short-range communicationmeans adapted to communicate optically. Shown is an example of anembodiment of infrared (IR) communication means/transceivers. Shown area receiver part (701) of the medical device part and a transmitter part(702) of an additional medical device. Alternatively, the medical devicepart and additional medical device is each provided with a receiver(701) and a transmitter (702) thereby enabling two-way communication.

FIG. 7 b illustrates an embodiment of the short-range communicationmeans adapted to communicate via an electrical switch. Shown is across-sectional view of an example of an embodiment of simplemechanical/electrical communication means in the form of switches. Shownare the communication switches of a medical device part (701) and of anadditional medical device (702). The communications switches (703; 703′)of the medical part (701) have an electric connection between them whenthe medical device part and additional device (701; 702) is not docked,fitted onto, in an interrelated communication position, etc. When thetwo devices (701; 702) are brought together then a first switch/switchpart (704) of the additional device (702) touches and moves the firstswitch/switch part (703) of the medical device part (701) therebyestablishing an electronic connection between them (703, 704) andbreaking the connection of switch/switch part (703) and (703′). Duringthe same movement a second switch/switch part (704′) of the additionaldevice (702) touches the second switch/switch part (703′) of the medicaldevice part (701) thereby establishing an electronic connection. Thebreaking of the connection between the first switch/switch part (703)and the second switch/switch part (703′) may determine whencommunication, transfer of information, etc. may be initiated.

The first (704) and second switch/switch part (704′) of the secondapparatus is preferably separated by an insulation layer (705).

FIG. 7 c illustrates an embodiment of the short-range communicationmeans adapted to communicate via inductive communication. Shown is anexample of an embodiment of simple inductive communication means wherecurrent induced in a resonance circuit is used to transfer information.Shown are a receiver part (701) of a medical device part and atransmitter part (702) of an additional medical device. Alternatively,the medical device part and the additional medical device is eachprovided with a receiver (701) and a transmitter (702) thereby enablingtwo-way communication.

1. A method of communicating medical data information between a medicaldevice part comprising: providing a medical device part which isapprovable according to preset validation standards for medical deviceparts, the medical device part comprising: at least one of a discrete orsubstantially continuous body fluid analysis means, a drugadministration means, a first processor and first storage means, a meansfor executing one or more medical related functions, and a physicalinterface; a communication part which is approvable according to presetvalidation standards for communication parts, the communication partcomprising: a second processor, a second storage means, a communicationmeans, and a physical interface; wherein the medical device part and thecommunication part exchanges data information according to apredetermined protocol, the exchange of data information via saidphysical interface according to a predetermined protocol, the exchangeof data information is under the control of the medical device partwherein the functionalities of each device part otherwise is separated,and wherein the communication part is optionally interchanged with asecond communication part without affecting the medical device partvalidation according to preset standards for medical device parts.
 2. Amethod according to claim 1, wherein the predetermined protocolcomprises the medical device part acting as a master and thecommunication device part acting as a slave where the exchange ofinformation is done by the medical device part polling the communicationdevice part.
 3. A method according to claim 2, wherein the medicaldevice part further comprises one or more of: a user interface, at leastone medical transducer, and a short-range communication means forexchanging data information with at least another medical device.
 4. Amethod according to claim 3, wherein the at least another medical deviceis selected from the group of: a drug administration device, a bodyfluid analyzer, an insulin administration device, a blood glucosemonitor (BGM), a continuous blood glucose monitor (CGM), an inhaler, atablet dispenser, a lipid monitor, a pulse monitor. a lancet device, astorage container, a balance, and any other apparatus adapted to measureat least one physiological parameter.
 5. A method according to claim 4,wherein the method further comprises controlling a power supply by themedical device part, where the power supply supplies the communicationdevice part with power.
 6. A method according to claims 5, wherein saidcommunication means communicates according to the Bluetooth protocol. 7.A method according to claim 6, wherein said communication meanscommunicates information according to one or more of: Radio frequency(RF) communication, Infrared (IR) communication, HTTP (Hyper TextTransmission Protocol), SHTTP (Secure Hyper Text Transmission Protocol),TCP/IP (Transmission Control Protocol/Internet Protocol), PPP(Point-to-Point), SSL (Secure Socket Layer), TLS (Transport LayerSecurity), and IrDA,
 8. A method according to claim 7, wherein saidcommunication means communicates with a wireless access point/a mobileterminal where the access point/the terminal communicates according toone or more of: GSM (Global System for Mobile communication), GPRS(General Packet Radio System), and UMTS (Universal Mobile TelephoneSystem).
 9. A method according to claim 8, wherein the communicationdevice part exchanges data information with a central server via awireless network access point.
 10. A method of supplying data from aportable medical device to a third party, the method comprising:automatically transmitting data information from a portable medicaldevice to a central server for storage in at least one database,processing said data information, in order to derive additionalinformation, and automatically transmitting at least a part of theadditional information to a predetermined third party.
 11. The methodaccording to claim 10, wherein said processing is done at said serverand/or at said medical device.
 12. The method according to claim 11,wherein said data information comprises information representing one ormore of: at least one blood glucose value, at least one valuerepresenting a body fluid level, at least one physiological parameter,amount and/or type of administered medication, amount and/or type ofadministered insulin, a trend of a glucose or body fluid level, aprediction of a glucose or body fluid level, timestamp in- or excludingdate, amount of food, measurement of physical activity, notification ofappointment, inventory logistics, and body characteristics. warnings,and symptoms.
 13. The method according to claim 12, wherein said step oftransmitting data information from a portable medical device to acentral server is done by transmitting said data information accordingto the Bluetooth protocol to a wireless access point connected via anetwork to the central server.
 14. The method according to claim 13,wherein said third parties are one or more of: at least one relative, atleast one parent, and at least one medical professional.
 15. The methodaccording to claim 14, wherein said method further comprisescommunicating between the portable medical device and another medicaldevice in order to retrieve relevant data information.
 16. A medicalsystem for assisting in the treatment of a human patient, the systemcomprising: a.) a medical part comprising: i.) hardware comprising acomputer readable medium encoded with a computer program, wherein themedical part is structured to be approvable according to presetvalidation standards for medical parts, and the computer readable mediumencoded with a computer program is configured to be approvable accordingto preset software validation standards for software, and ii.) a medicalpart processor; b.) a communication part that comprises a communicationmeans for communicating with other devices; c.) a physical interfacebetween the medical part and the communication part; and d.) aninterface layer that facilitates communication across the physicalinterface, wherein the interface layer is under control of the medicalpart processor; and wherein the communication part is structured to beinterchanged with a second communication part without affecting themedical part or software validation according to preset standards formedical parts and software.
 17. The system of claim 16, wherein at leastone of the medical part and the communication part further comprises astorage unit for storing data.
 18. The system of claim 16, wherein themedical part acts a master and the communication part acts as a slave.19. The system of claim 16, wherein the medical part is capable ofperforming medical functionalities and the communication means iscapable of performing communication functionalities and wherein thecommunication functionalities and medical functionalities are separatedfrom each other.
 20. The system of claim 16, wherein the computerprogram comprises at least one of software or firmware.